-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS-57824 added Known Issues section to cert-manager release notes #96128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
5860ffa
to
ff85fe4
Compare
🤖 Wed Jul 16 16:01:21 - Prow CI generated the docs preview: |
[id="cert-manager-operator-1-16-1-known-issues_{context}"] | ||
=== Known Issues | ||
|
||
When using the Venafi issuer with username/password authentication in cert-manager versions 1.16.0 and later, the default client ID is hardcoded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] RedHat.TermsErrors: Use 'hard-coded' rather than 'hardcoded'. For more information, see RedHat.TermsErrors.
ff85fe4
to
778010c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to add this into 1.16.0 section (this place:
[id="cert-manager-operator-1-16-1-known-issues_{context}"] | ||
=== Known Issues | ||
|
||
When using the Venafi issuer with username/password authentication in cert-manager versions 1.16.0 and later, the default client ID is hard-coded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When using the Venafi issuer with username/password authentication in cert-manager versions 1.16.0 and later, the default client ID is hard-coded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. | |
When using the Venafi issuer with username/password authentication in cert-manager version 1.16.0, the default client ID is hard-coded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. |
778010c
to
fc62483
Compare
/lgtm |
/label peer-review-needed |
/label peer-review-in-progress |
@@ -85,6 +85,11 @@ The peak memory use of the cert-manager components when they start up is optimiz | |||
* link:https://access.redhat.com/security/cve/CVE-2024-45338[CVE-2024-45338] | |||
* link:https://access.redhat.com/security/cve/CVE-2025-22866[CVE-2025-22866] | |||
|
|||
[id="cert-manager-operator-1-16-0-known-issues_{context}"] | |||
=== Known Issues | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wgabor0427 I'm not familiar with this product or this section of the docs, so I'm just sharing some ideas and observations:
- I would consider writing out "username and password authentication"
- Typically, Red Hat refrains from pre-announcing features, bug fixes, etc. because in the past there have been incidents where a fix was announced but not delivered in the release mentioned. This can causes confustion for both customers and the Support organization, so I would remove the remove the reference to 1.17.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typically, Red Hat refrains from pre-announcing features, bug fixes, etc
@rh-tokeefe Thanks for pointing this out! This fix is merged and we could confirm 1.17.0 will contain this fix. In this situation, could we mention the version explicitly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please ignore my comment. I'm fine with the latest change
@wgabor0427 a couple of minor suggestions I think you should consider before sending this on to merge review. |
/label peer-review-done |
/remove-label peer-review-in-progress |
fc62483
to
f8aa021
Compare
f8aa021
to
89d2f2b
Compare
@wgabor0427: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/lgtm |
Version(s):
4.14+
Issue:
https://issues.redhat.com/browse/OCPBUGS-57824
Link to docs preview:
https://96128--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/cert_manager_operator/cert-manager-operator-release-notes.html
QE review:
Additional information: